Promised AF4 Revision
Original Post
Quite a long time ago I said that I was working on a revision of AF4. Since then I have been working away on it, and here it is. It's turned out to be very different from AF4, but has incorporated many of the things we have been recently discussing on the Forum. I have been finding the grouping of tasks into New, Old, Recurring and Unfinished extremely powerful.
Here's how it's done:
• It's best to use a lined notebook. The size of the page and the number of lines doesn't matter too much. (I'm assuming in these instructions that you will be using paper and pen, but it's easy to duplicate electronically)
• Start by heading three successive pages of your notebook "New", "Recurring" and "Unfinished" respectively.
• Then on the first page write down about 10-20 tasks that you need to do, and draw a line under them. These are your initial "Old Tasks". As you think of other tasks or they arise in the course of your work, add them below the line. These are your "New Tasks".
• Go through all the "Old Tasks" in order. Whenever a tasks feels ready to be done, work on it.
• If you finish the task completely, cross it off the list. If it's a recurring task, re-enter it on the "Recurring" page. If you haven't finished the task, re-enter it on the "Unfinished" page.
• At this stage you only work on the Old Tasks, ignoring the others. Continue circulating through the Old Tasks until no more of them feel ready to be done for the moment. Now start working on the New Tasks (which are the ones below the line, remember).
• When you've done as much work as you want to do on New Tasks for the time being, deal with the "Recurring" page and then the "Unfinished" page in the same way - except that there is no line dividing these pages. Once you have done all the tasks you want to do on the Unfinished page, return to the Old Tasks. You must do at least one task (hopefully more), otherwise all remaining Old Tasks are dismissed. Please note that only Old Tasks are liable to be dismissed. New Tasks, Recurring Tasks and Unfinished Tasks are not dismissed.
• Once all the Old Tasks have been done or dismissed, a new line is drawn and the existing New Tasks are re-designated as Old Tasks.
• Any time you fill a page with tasks, continue the same heading onto a new page. Then when you are working on each particular type of task circulate through all the pages with that heading.
Here's how it's done:
• It's best to use a lined notebook. The size of the page and the number of lines doesn't matter too much. (I'm assuming in these instructions that you will be using paper and pen, but it's easy to duplicate electronically)
• Start by heading three successive pages of your notebook "New", "Recurring" and "Unfinished" respectively.
• Then on the first page write down about 10-20 tasks that you need to do, and draw a line under them. These are your initial "Old Tasks". As you think of other tasks or they arise in the course of your work, add them below the line. These are your "New Tasks".
• Go through all the "Old Tasks" in order. Whenever a tasks feels ready to be done, work on it.
• If you finish the task completely, cross it off the list. If it's a recurring task, re-enter it on the "Recurring" page. If you haven't finished the task, re-enter it on the "Unfinished" page.
• At this stage you only work on the Old Tasks, ignoring the others. Continue circulating through the Old Tasks until no more of them feel ready to be done for the moment. Now start working on the New Tasks (which are the ones below the line, remember).
• When you've done as much work as you want to do on New Tasks for the time being, deal with the "Recurring" page and then the "Unfinished" page in the same way - except that there is no line dividing these pages. Once you have done all the tasks you want to do on the Unfinished page, return to the Old Tasks. You must do at least one task (hopefully more), otherwise all remaining Old Tasks are dismissed. Please note that only Old Tasks are liable to be dismissed. New Tasks, Recurring Tasks and Unfinished Tasks are not dismissed.
• Once all the Old Tasks have been done or dismissed, a new line is drawn and the existing New Tasks are re-designated as Old Tasks.
• Any time you fill a page with tasks, continue the same heading onto a new page. Then when you are working on each particular type of task circulate through all the pages with that heading.
Reply by leon
Good morning Mark!
Thanks for offering us up a new system to work with.
My initial feeling is that I like the look of this.
Specifically, I like the grouping into 3 page types (I'm sure Gerry would approve too!)
I often start new projects and regularly do not finish them (at home anyway). Hopefully writing new tasks on the respective page will help me stay aware of new tasks I am taking on.
One question: Are you putting review / waiting for type items onto the 'unfinished' pages. My guess is that it would be similar to autofocus. I.e. put it on the unfinished page if it's due within a few days or write a calender review date if it's several weeks away. Is this so?
Thanks for offering us up a new system to work with.
My initial feeling is that I like the look of this.
Specifically, I like the grouping into 3 page types (I'm sure Gerry would approve too!)
I often start new projects and regularly do not finish them (at home anyway). Hopefully writing new tasks on the respective page will help me stay aware of new tasks I am taking on.
One question: Are you putting review / waiting for type items onto the 'unfinished' pages. My guess is that it would be similar to autofocus. I.e. put it on the unfinished page if it's due within a few days or write a calender review date if it's several weeks away. Is this so?
Reply by Roger J
Hello Mark,
Just a couple of things after a quick read through:
Are not the 'Columns' actually the Recurring and Unfinished Pages?
I haven't yet tried this new approach and may not do so until I've been running my DWM2 notebook for a bit and read other reactions/feedback. I wonder if the three page types might not get mixed up and 'interfere' with the processing in that one will be paging through other page types looking for the next location of the type one is working on.
Maybe a notebook with moveable pages would be more suitable so that the New (with its Old tasks), Unfinished and Recurring tasks remain with each other.
Just a couple of things after a quick read through:
Are not the 'Columns' actually the Recurring and Unfinished Pages?
I haven't yet tried this new approach and may not do so until I've been running my DWM2 notebook for a bit and read other reactions/feedback. I wonder if the three page types might not get mixed up and 'interfere' with the processing in that one will be paging through other page types looking for the next location of the type one is working on.
Maybe a notebook with moveable pages would be more suitable so that the New (with its Old tasks), Unfinished and Recurring tasks remain with each other.
Reply by Will
Thanks, Mark.
I rather fear that by the time I've given SAF a proper go, this will be ancient history.
I rather fear that by the time I've given SAF a proper go, this will be ancient history.
Reply by leon
Hi Mark,
On reviewing DWM2 and Roger's thoughts, do you consider DWM2 as being a more elgant system than revised AF4? What, in your experience, are the relative strengths & weaknesses with your revised AF4 System compared with your other systems?
On reviewing DWM2 and Roger's thoughts, do you consider DWM2 as being a more elgant system than revised AF4? What, in your experience, are the relative strengths & weaknesses with your revised AF4 System compared with your other systems?
Reply by Margaret1
Thanks, Mark. I'm going to jump right in and try it now.
First task is "Separate current DWM2 list into Revised AF4 categories".
Best wishes.
First task is "Separate current DWM2 list into Revised AF4 categories".
Best wishes.
Reply by Jessica O
I like these new ideas for AF. I just rebooted my AF list using some of Alan's ideas about separate project lists and am going through it using a post-it note to collect tasks when several attack my brain at once (a little like SAF and someone's (I don't recall who) separate moving page idea).
Pulling things out into projects and leaving a note about the project and/or top tasks on the AF list is helping keep me more organized. I think that pulling out recurring tasks will do the same.
Thanks for all the ideas!
Pulling things out into projects and leaving a note about the project and/or top tasks on the AF list is helping keep me more organized. I think that pulling out recurring tasks will do the same.
Thanks for all the ideas!
Reply by Alan Baljeu
Sounds like how My System once worked. It also had an AF4 list and separated out the unfinished tasks, and it worked well.
A big difference is that you never dismiss Unfinished tasks or Recurring tasks. This surprises me. Where then is the push to clear Unfinished tasks?
A big difference is that you never dismiss Unfinished tasks or Recurring tasks. This surprises me. Where then is the push to clear Unfinished tasks?
Reply by Mark Forster
leon:
<< Are you putting review / waiting for type items onto the 'unfinished' pages. My guess is that it would be similar to autofocus. I.e. put it on the unfinished page if it's due within a few days or write a calender review date if it's several weeks away. Is this so? >>
That sort of task I usually put under New Tasks because I have finished everything I can do on the subject for the time being. The review is intended to check whether further action is possible/needed.
Yes, if it's more than a few days away put it in some form of reminder, rather than on the list.
<< Are you putting review / waiting for type items onto the 'unfinished' pages. My guess is that it would be similar to autofocus. I.e. put it on the unfinished page if it's due within a few days or write a calender review date if it's several weeks away. Is this so? >>
That sort of task I usually put under New Tasks because I have finished everything I can do on the subject for the time being. The review is intended to check whether further action is possible/needed.
Yes, if it's more than a few days away put it in some form of reminder, rather than on the list.
Reply by Mark Forster
Roger J:
<< Are not the 'Columns' actually the Recurring and Unfinished Pages? >>
Oops, yes, that's a left over from an earlier draft which I have failed to amend. I will change it.
<< Are not the 'Columns' actually the Recurring and Unfinished Pages? >>
Oops, yes, that's a left over from an earlier draft which I have failed to amend. I will change it.
Reply by Mark Forster
Roger J:
<< I wonder if the three page types might not get mixed up and 'interfere' with the processing in that one will be paging through other page types looking for the next location of the type one is working on. >>
It's not proved too much of a problem for me. I certainly prefer it to having separate columns which I tried at an earlier stage.
<< I wonder if the three page types might not get mixed up and 'interfere' with the processing in that one will be paging through other page types looking for the next location of the type one is working on. >>
It's not proved too much of a problem for me. I certainly prefer it to having separate columns which I tried at an earlier stage.
Reply by Mark Forster
Roger J:
<< Maybe a notebook with moveable pages would be more suitable so that the New (with its Old tasks), Unfinished and Recurring tasks remain with each other. >>
Yes, I'm sure that would be an excellent solution. Personally I don't like notebooks with moveable pages, but that doesn't stop anyone else from trying it.
<< Maybe a notebook with moveable pages would be more suitable so that the New (with its Old tasks), Unfinished and Recurring tasks remain with each other. >>
Yes, I'm sure that would be an excellent solution. Personally I don't like notebooks with moveable pages, but that doesn't stop anyone else from trying it.
Reply by Mark Forster
Leon:
<< On reviewing DWM2 and Roger's thoughts, do you consider DWM2 as being a more elgant system than revised AF4? What, in your experience, are the relative strengths & weaknesses with your revised AF4 System compared with your other systems? >>
I don't know that elegant is the right word. Having three different types of page and four different categories of task is not very elegant, but I think the advantages outweigh the disadvantages.
The main advantages are that it makes it much easier to see where you are getting stuck and why, and gives you a greatly improved sense of how your work is progressing. If you find yourself getting bogged down in loads of trivial tasks, then you can slash the number of recurring tasks you have. If you have too many unfinished tasks, then you need to look at the number of time-consuming commitments you have made.
I also find that having Recurring and Unfinished tasks grouped helps me to deal with them more effectively.
Another effect is that the number of New Tasks is drastically reduced. This speeds up the AF4 process.
<< On reviewing DWM2 and Roger's thoughts, do you consider DWM2 as being a more elgant system than revised AF4? What, in your experience, are the relative strengths & weaknesses with your revised AF4 System compared with your other systems? >>
I don't know that elegant is the right word. Having three different types of page and four different categories of task is not very elegant, but I think the advantages outweigh the disadvantages.
The main advantages are that it makes it much easier to see where you are getting stuck and why, and gives you a greatly improved sense of how your work is progressing. If you find yourself getting bogged down in loads of trivial tasks, then you can slash the number of recurring tasks you have. If you have too many unfinished tasks, then you need to look at the number of time-consuming commitments you have made.
I also find that having Recurring and Unfinished tasks grouped helps me to deal with them more effectively.
Another effect is that the number of New Tasks is drastically reduced. This speeds up the AF4 process.
Reply by Mark Forster
Margaret:
<< First task is "Separate current DWM2 list into Revised AF4 categories".>>
Actually the first step is to enter all tasks into New Tasks. They only get categorised once they have had some action taken on them.
<< First task is "Separate current DWM2 list into Revised AF4 categories".>>
Actually the first step is to enter all tasks into New Tasks. They only get categorised once they have had some action taken on them.
Reply by Mark Forster
Alan:
<< Where then is the push to clear Unfinished tasks? >>
Just the fact that they are Unfinished.
<< Where then is the push to clear Unfinished tasks? >>
Just the fact that they are Unfinished.
Reply by Alan Baljeu
Earlier you wrote that your new version of AF4 would be happier with larger-grained tasks than some other systems. Is that the case here?
Reply by Sarah
I'm giving it a shot... It was trivial to set up four folders on Toodledo to manage each of the headings. We'll see how it goes... I really love the timed dismissal of DWM so going back to something without it may be interesting.
Reply by Roger J
Reply by Margaret1
Thanks, Mark - of couse you're right. I'll let you know how I get on. I hope the excitement of having a new system to play with doesn't drown out the fact that the best way to get things done is to do them, as I think you pointed out a while back.
Reply by Mark Forster
Alan:
<< Earlier you wrote that your new version of AF4 would be happier with larger-grained tasks than some other systems. Is that the case here? >>
Yes, I think that's right. I am for instance putting entire books into it as one task, e.g. "Read War and Peace", rather than "Read War and Peace, Chapter 1". That wouldn't work in 3-T because a task that large would occupy the slot for weeks (or, as when I actually read War and Peace, years).
<< Earlier you wrote that your new version of AF4 would be happier with larger-grained tasks than some other systems. Is that the case here? >>
Yes, I think that's right. I am for instance putting entire books into it as one task, e.g. "Read War and Peace", rather than "Read War and Peace, Chapter 1". That wouldn't work in 3-T because a task that large would occupy the slot for weeks (or, as when I actually read War and Peace, years).
Reply by Mark Forster
Roger J:
I distinguish between dismissing a task, which is the result of a rule-based system, and deleting a task. In all my systems one is always free to delete a task at any time. This system makes it easier to audit one's list and delete tasks accordingly.
I distinguish between dismissing a task, which is the result of a rule-based system, and deleting a task. In all my systems one is always free to delete a task at any time. This system makes it easier to audit one's list and delete tasks accordingly.
Reply by Mark Forster
There's a big article on Autofocus and this latest variant on the Life Hacker site today:
http://lifehacker.com/5704856/the-autofocus-productivity-method-stop-maintaining-to+do-lists-and-start-getting-stuff-done
http://lifehacker.com/5704856/the-autofocus-productivity-method-stop-maintaining-to+do-lists-and-start-getting-stuff-done
Reply by Vegheadjones
Great article! Moving from an electronic DWM AF4 system to an analog SAF one, I find this to be very true:
"I and many others found that working the list resulted in an almost meditative state in which resistance and procrastination seemed to melt away and the task of the moment became for that moment the focus of one's universe. "
"I and many others found that working the list resulted in an almost meditative state in which resistance and procrastination seemed to melt away and the task of the moment became for that moment the focus of one's universe. "
Reply by Kiwi Erik
This sounds promising!
There's one thing in Mark's instructions that I found a bit confusing: Mark says to set up three pages in the notebook with the headings "New", "Recurring" and "Unfinished". The next instruction is to:
<<...write down about 10-20 tasks that you need to do, and draw a line under them. These are your initial "Old Tasks". As you think of other tasks or they arise in the course of your work, add them below the line. These are your "New Tasks".>>
But which page should this list of 10-20 tasks be placed on to? I'm guessing that it should be the "New" page, though it could just as easily be the next blank page in the notebook, or somewhere else. It'd be good to know exactly which page these tasks should go on...
There's one thing in Mark's instructions that I found a bit confusing: Mark says to set up three pages in the notebook with the headings "New", "Recurring" and "Unfinished". The next instruction is to:
<<...write down about 10-20 tasks that you need to do, and draw a line under them. These are your initial "Old Tasks". As you think of other tasks or they arise in the course of your work, add them below the line. These are your "New Tasks".>>
But which page should this list of 10-20 tasks be placed on to? I'm guessing that it should be the "New" page, though it could just as easily be the next blank page in the notebook, or somewhere else. It'd be good to know exactly which page these tasks should go on...
Reply by JD
Mark:
<>
<>
The New Tasks (those below the line): in the original AF4 they were worked on in order, ie by a single pass though the list before returning to the Old Tasks. Are the New Tasks still worked on in this way? Or are they worked on the circulating stand-out principle (ie continue going around them until none stand out)?
If its the latter, then it appears to be a variance to the original AF4 way of working. The Closed List gets worked on in a circulating fashion, the Open List gets worked on in a single pass fashion in the original AF4.
<
<
The New Tasks (those below the line): in the original AF4 they were worked on in order, ie by a single pass though the list before returning to the Old Tasks. Are the New Tasks still worked on in this way? Or are they worked on the circulating stand-out principle (ie continue going around them until none stand out)?
If its the latter, then it appears to be a variance to the original AF4 way of working. The Closed List gets worked on in a circulating fashion, the Open List gets worked on in a single pass fashion in the original AF4.
Reply by Sarah
I had to go back and reread the directions when I got to that point, too. I'm interpreting "in the same way" as meaning round and round until nothing stands out, only without the possibility of dismissal. ("Please note that only Old Tasks are liable to be dismissed. New Tasks, Recurring Tasks and Unfinished Tasks are not dismissed.")
Mark? What was your intent here?
Mark? What was your intent here?
Reply by Mark Forster
Kiwi Erik:
<< But which page should this list of 10-20 tasks be placed on to? >>
Sorry this isn't as clear as it should be. They are new tasks so they should go on the New Tasks page - they are then immediately transformed into Old Tasks when the line is drawn. I've amended it to make it clear.
<< But which page should this list of 10-20 tasks be placed on to? >>
Sorry this isn't as clear as it should be. They are new tasks so they should go on the New Tasks page - they are then immediately transformed into Old Tasks when the line is drawn. I've amended it to make it clear.
Reply by Alan Baljeu
"I and many others found that working the list resulted in an almost meditative state in which resistance and procrastination seemed to melt away and the task of the moment became for that moment the focus of one's universe. "
Thanks for the clue. That totally clarifies where I'm going wrong today. I'm overcomplicating. Setting the above as my goal.
Thanks for the clue. That totally clarifies where I'm going wrong today. I'm overcomplicating. Setting the above as my goal.
Reply by Mark Forster
JD:
<< Are the New Tasks still worked on in this way? Or are they worked on the circulating stand-out principle (ie continue going around them until none stand out)? >>
This is a change to AF4. All the four types of task (Old, New, Recurring and Unfinished) are worked on the circulating stand-out principle.
<< Are the New Tasks still worked on in this way? Or are they worked on the circulating stand-out principle (ie continue going around them until none stand out)? >>
This is a change to AF4. All the four types of task (Old, New, Recurring and Unfinished) are worked on the circulating stand-out principle.
Reply by Mark Forster
Sarah:
<< Mark? What was your intent here? >>
Because re-entered tasks are not put onto the "New" page, the number of New Tasks is vastly reduced from AF4. This changes the dynamics between the closed list and the open list, so it makes more sense to treat all four types of task (Old, New, Recurring, Unfinished) the same.
<< Mark? What was your intent here? >>
Because re-entered tasks are not put onto the "New" page, the number of New Tasks is vastly reduced from AF4. This changes the dynamics between the closed list and the open list, so it makes more sense to treat all four types of task (Old, New, Recurring, Unfinished) the same.
Reply by Sarah
Makes sense, thanks for clarifying! That's definitely what I'm seeing... I dumped my whole existing list as "old" (I know, I know...) so it started at 40ish tasks... and right now at the end of one full working day I've got 23 Old, 6 New, 4 Recurring, and 5 Unfinished.
Reply by Seraphim
I found the same results (preponderance of recurring tasks, relatively small number of actually new tasks) when I broke up my DWM list into six categories:
Work Hotlist
Work Maintenance
Work Misc
Personal Hotlist
Personal Maintenance
Personal Misc
The Hotlists roughly equate to the Unfinished -- current key work that I'm trying to finish.
The Maintenance lists equate to the Recurring.
The Misc lists roughly equate to the New. What I've found is that I actually look at these lists very rarely.
New items that I initially add to the Misc lists, but then actually turn out to be really important, I just move them to the Hotlists.
I still keep those lists in Outlook, but I've been "driving" the whole system with a little SuperFocus notebook. It prompts me to go check the different lists. Often I just write hot tasks directly into SuperFocus.
Personally, I'd really be cautious about moving to this new AF4 revision, because it seems to lack the control of the SuperFocus 2nd column feature. And my DWM backend system in Outlook works very similarly to the new AF4 revision already.
Work Hotlist
Work Maintenance
Work Misc
Personal Hotlist
Personal Maintenance
Personal Misc
The Hotlists roughly equate to the Unfinished -- current key work that I'm trying to finish.
The Maintenance lists equate to the Recurring.
The Misc lists roughly equate to the New. What I've found is that I actually look at these lists very rarely.
New items that I initially add to the Misc lists, but then actually turn out to be really important, I just move them to the Hotlists.
I still keep those lists in Outlook, but I've been "driving" the whole system with a little SuperFocus notebook. It prompts me to go check the different lists. Often I just write hot tasks directly into SuperFocus.
Personally, I'd really be cautious about moving to this new AF4 revision, because it seems to lack the control of the SuperFocus 2nd column feature. And my DWM backend system in Outlook works very similarly to the new AF4 revision already.
Reply by Seraphim
Mark, any thoughts of integrating the SuperFocus 2nd column feature into AF4 revised?
Or, going the other direction, any thoughts of perhaps integrating the different page types into SuperFocus? Seems like that would be pretty simple, actually. You could just use the AF dismissal rules, rather than AF4 dismissal rules, and thus have only three types of tasks, New (never touched), Recurring, and Unfinished.
Or any thoughts in general on how AF4 Revised compares with SuperFocus?
Or, going the other direction, any thoughts of perhaps integrating the different page types into SuperFocus? Seems like that would be pretty simple, actually. You could just use the AF dismissal rules, rather than AF4 dismissal rules, and thus have only three types of tasks, New (never touched), Recurring, and Unfinished.
Or any thoughts in general on how AF4 Revised compares with SuperFocus?
Reply by Alan Baljeu
What happens when the New page is full? When the recurring or unfinished pages get full? Seems to me in a notebook you start to get a mix of pages like new/recurring/new/unfinished/unfinished/recurring. Will processing get awkward or do you mostly take it one page at a time?
Reply by Mark Forster
Seraphim:
Lots to think about in your posts - and, no, I haven't thought about any of it yet!
Lots to think about in your posts - and, no, I haven't thought about any of it yet!
Reply by Mark Forster
Alan:
Yes, you do get a mix of pages. My currently active pages are new/recurring/unfinished/new/new/recurring/recurring.
It sounds confusing, but in practice I don't find it so. If I'm working on New for example, when I get to the end of one New page I just page forward until I come to the next. It helps if the pages are clearly marked of course.
Another solution, as Roger J proposed earlier, is to use a loose-leaf notebook.
Yes, you do get a mix of pages. My currently active pages are new/recurring/unfinished/new/new/recurring/recurring.
It sounds confusing, but in practice I don't find it so. If I'm working on New for example, when I get to the end of one New page I just page forward until I come to the next. It helps if the pages are clearly marked of course.
Another solution, as Roger J proposed earlier, is to use a loose-leaf notebook.
Reply by Mark Forster
Sarah:
<< I've got 23 Old, 6 New, 4 Recurring, and 5 Unfinished. >>
At the end of today I have 9 Old, 6 New, 32 Recurring and 3 Unfinished. I can see from those figures immediately that I have far too many recurring tasks, and if I cut them right back I would finish all my work in no time at all!
<< I've got 23 Old, 6 New, 4 Recurring, and 5 Unfinished. >>
At the end of today I have 9 Old, 6 New, 32 Recurring and 3 Unfinished. I can see from those figures immediately that I have far too many recurring tasks, and if I cut them right back I would finish all my work in no time at all!
Reply by Erik
Any system really benefits from a separation between New/Old/Unfinished (Projects) with Recurring (Maintenance). When a project is finished, it often creates roots that need to be tended to (maintenance) without our being conscious of it. Any way of actually figuring out the numbers and forcibly limit them is a boon to one's time.
Reply by Margaret1
Mark wrote:
Mark, I'd be interested to know what your recurring tasks consist of. Most of mine are things that I feel I wouldn't want to, or be able to, cut back on, such as laundry, housework, check e-mail, do paperwork, phone family and friends, meals+clear.
Mark, I'd be interested to know what your recurring tasks consist of. Most of mine are things that I feel I wouldn't want to, or be able to, cut back on, such as laundry, housework, check e-mail, do paperwork, phone family and friends, meals+clear.
Reply by Mark Forster
Margaret1:
The point I was making was that the figures enable me to see where I can make improvements in my personal time management. Your figures may show something entirely different. If I were to cut back my recurring tasks, I certainly wouldn't be cutting the ones you mention (though it might be worth looking to see if there are ways of cutting down the time they take - email for instance often takes much more time than it needs to).
The point I was making was that the figures enable me to see where I can make improvements in my personal time management. Your figures may show something entirely different. If I were to cut back my recurring tasks, I certainly wouldn't be cutting the ones you mention (though it might be worth looking to see if there are ways of cutting down the time they take - email for instance often takes much more time than it needs to).
Reply by Roger J
This must be one of the 'fastest' new threads in the Forum!
<>
I do not think 32 x Recurring is too many, much of everyday stuff is little tasks. Margaret's post has six in a one line example.
The key, I think, and Seraphim and others have mentioned this, is to find a way of batching and/or processing such Recurring tasks. Wasn't it nuntym who several weeks ago brought in the concept of these tasks as being of a maintenance type and need to be processed in a certain way for efficiency's sake?
One problem is that consolidating such tasks under one or a few headings leads to the danger of some individual tasks not being done. I've got a personality, and now a matching ag,e that lends itself to forgetting things, which is one reason I've coped better since AF arrived nearly two years ago.
I combat this deficiency of my own with extensive checklists, especially for work travel where arriving at a foreign destination with something missing can be a right burden. Not having a spare power unit for my notebook computer is not a problem in Durban or Damascus, but it is in Solwezi or Mkuu-Rombo.
I've been tackling these 'maintenance' recurring tasks by entering each relevant one into lists called:
- First thing morning: eg turn heating system on, check overnight email, schedule for the day,AF/DWM list, take garbage downstairs when leaving, medication.
- Work stuff: these are items to be packed into my work bag (backpack or briefcase) or to carry/have about my person.
- Mid-Morning: Check email (I turn off automatic sending/receiving to minimise distractions), reviewAF/DWM, make/return calls or messages.
- Break: as above plus a snack and soup.
- Afternoon: as above, plus check errands to do en route back to apartment (all errand items are written in a Moleskine pocket notebook which I always carry with me everywhere, and which serves a capture point if my AF/DWM book isn't with me).
- Arrival apartment: set up computer notebook on desk, review AF/DWM, reduce Inbox to zero, go through new entries in Moleskine pocket book, save new passwords, incremental backup etc.
I also have a Weekly and a Monthly Maintenance list with additional tasks to the daily stuff, such as a weekly full backup, review medication stock, monthly battery swap/recharge, clean IT kit etc.
These maintenance tasks are all in a ListPro file which is available on my smartphone (WM 6.5, no iPhone for me, yet). I am able to tick off the applicable ones, then clear the tick boxes for the next day when I'm done.
And yes, sometimes I might forget to use the list, so I may still enter a forgotten task into my AF/DWM list. Some days a task item might not be applicable, but it's still on the list if does need to be ticked, eg green box medication ok?
Works for me.
<
I do not think 32 x Recurring is too many, much of everyday stuff is little tasks. Margaret's post has six in a one line example.
The key, I think, and Seraphim and others have mentioned this, is to find a way of batching and/or processing such Recurring tasks. Wasn't it nuntym who several weeks ago brought in the concept of these tasks as being of a maintenance type and need to be processed in a certain way for efficiency's sake?
One problem is that consolidating such tasks under one or a few headings leads to the danger of some individual tasks not being done. I've got a personality, and now a matching ag,e that lends itself to forgetting things, which is one reason I've coped better since AF arrived nearly two years ago.
I combat this deficiency of my own with extensive checklists, especially for work travel where arriving at a foreign destination with something missing can be a right burden. Not having a spare power unit for my notebook computer is not a problem in Durban or Damascus, but it is in Solwezi or Mkuu-Rombo.
I've been tackling these 'maintenance' recurring tasks by entering each relevant one into lists called:
- First thing morning: eg turn heating system on, check overnight email, schedule for the day,AF/DWM list, take garbage downstairs when leaving, medication.
- Work stuff: these are items to be packed into my work bag (backpack or briefcase) or to carry/have about my person.
- Mid-Morning: Check email (I turn off automatic sending/receiving to minimise distractions), reviewAF/DWM, make/return calls or messages.
- Break: as above plus a snack and soup.
- Afternoon: as above, plus check errands to do en route back to apartment (all errand items are written in a Moleskine pocket notebook which I always carry with me everywhere, and which serves a capture point if my AF/DWM book isn't with me).
- Arrival apartment: set up computer notebook on desk, review AF/DWM, reduce Inbox to zero, go through new entries in Moleskine pocket book, save new passwords, incremental backup etc.
I also have a Weekly and a Monthly Maintenance list with additional tasks to the daily stuff, such as a weekly full backup, review medication stock, monthly battery swap/recharge, clean IT kit etc.
These maintenance tasks are all in a ListPro file which is available on my smartphone (WM 6.5, no iPhone for me, yet). I am able to tick off the applicable ones, then clear the tick boxes for the next day when I'm done.
And yes, sometimes I might forget to use the list, so I may still enter a forgotten task into my AF/DWM list. Some days a task item might not be applicable, but it's still on the list if does need to be ticked, eg green box medication ok?
Works for me.
Reply by Mark Forster
Roger:
Whether 32 Recurring Tasks is too many or not depends on your circumstances. I know I could cut down the number considerably in my life, but of course that may be quite different for other people.
I think checklists are a great idea, particularly in the sort of circumstances you mention. For years I was out giving presentations to church groups every night of the week, and I always used a check list to make sure I hadn't forgotten anything.
I note that the checklists you mention are for particular times, such as first thing in the morning, packing for work, and so on. I don't recommend that tasks which have to be done at a particular time should be on an Autofocus list. AF is for managing unscheduled tasks.
Whether 32 Recurring Tasks is too many or not depends on your circumstances. I know I could cut down the number considerably in my life, but of course that may be quite different for other people.
I think checklists are a great idea, particularly in the sort of circumstances you mention. For years I was out giving presentations to church groups every night of the week, and I always used a check list to make sure I hadn't forgotten anything.
I note that the checklists you mention are for particular times, such as first thing in the morning, packing for work, and so on. I don't recommend that tasks which have to be done at a particular time should be on an Autofocus list. AF is for managing unscheduled tasks.
Reply by Roger J
Mark,
Oops, I forgot to mention that the maintenance tasks referred to in my previous posting do not appear anywhere in my AF/DWM list. They reside in Listpro and are triggered by an Outlook alarm at the appropriate time. I use Outlook for hard schedule appointments and regular recurring tasks.
I just have to have these checklists because although I've tried to make them habits, sometimes I forget the basic stuff when I leave the apartment or office, eg passport (advisable to carry it here in Damascus, or at least a colour copy of the main page and current visa - note to self: scan passport, print copies, carry in wallet/work bag), even my watch or phone now and again.
Of course, little reminders not in Listpro DO appear on AF/DWM, eg "Put new camera in work bag before end of day".
BTW, you need to correct that 'Columns' error in the Lifehacker copy as well, just in case.
Oops, I forgot to mention that the maintenance tasks referred to in my previous posting do not appear anywhere in my AF/DWM list. They reside in Listpro and are triggered by an Outlook alarm at the appropriate time. I use Outlook for hard schedule appointments and regular recurring tasks.
I just have to have these checklists because although I've tried to make them habits, sometimes I forget the basic stuff when I leave the apartment or office, eg passport (advisable to carry it here in Damascus, or at least a colour copy of the main page and current visa - note to self: scan passport, print copies, carry in wallet/work bag), even my watch or phone now and again.
Of course, little reminders not in Listpro DO appear on AF/DWM, eg "Put new camera in work bag before end of day".
BTW, you need to correct that 'Columns' error in the Lifehacker copy as well, just in case.
Reply by Mark Forster
Roger J:
<< you need to correct that 'Columns' error in the Lifehacker copy as well, just in case. >>
I can ask them to correct it - but I've no control over whether they do or not.
<< you need to correct that 'Columns' error in the Lifehacker copy as well, just in case. >>
I can ask them to correct it - but I've no control over whether they do or not.
Reply by Alan Baljeu
I like reducing things to their essence, and in this case it seems to be:
Focus over three lists:
- things you might do, divided into new and old
- things you started doing
- things you do regularly
Focus over three lists:
- things you might do, divided into new and old
- things you started doing
- things you do regularly
Reply by Roger J
Alan:
Thanks for that neat appraisal, makes a lot of sense.
Out of interest, will you be revamping your OneNote system for work? I can see re-jigging within OneNote is so easy.
I still prefer to keep work and non-work lists separate, however, it may be feasible for some to have two columns on each page, one for Work, the other for Personal, but still subject to the AF4R rules. Another approach could be Personal on LH pages, Work on RH pages.
I would also try to keep the New/Old Tasks, Unfinished/in progress, and Recurring is separate parts of any paper system as well.
Thanks for that neat appraisal, makes a lot of sense.
Out of interest, will you be revamping your OneNote system for work? I can see re-jigging within OneNote is so easy.
I still prefer to keep work and non-work lists separate, however, it may be feasible for some to have two columns on each page, one for Work, the other for Personal, but still subject to the AF4R rules. Another approach could be Personal on LH pages, Work on RH pages.
I would also try to keep the New/Old Tasks, Unfinished/in progress, and Recurring is separate parts of any paper system as well.
Reply by Erik
Haha, just figured I REALLY prefer this kind of categorizing to GTD contexts!!!
Reply by Roger J
Hi Erik,
I know what you mean!
To be fair, it was GTD that got me interested again in task management, but I just could not handle the system/concept 'overhead'.
That said, I do sometimes use contexts to decide where and when I can do certain tasks.
The best example occurred last year when I was working in rural Zambia for a month and the broadband access via the mobile phone network was awful. This meant I could not file my UK VAT (sales/purchase tax) quarterly return online until I was in Johannesburg airport en route home where the access was great and I could catch up plus do a lot of email processing.
That was back in the early days of AutoFocus and I recall tagging some tasks 'JNB' = Johannesburg International Airport code.
I know what you mean!
To be fair, it was GTD that got me interested again in task management, but I just could not handle the system/concept 'overhead'.
That said, I do sometimes use contexts to decide where and when I can do certain tasks.
The best example occurred last year when I was working in rural Zambia for a month and the broadband access via the mobile phone network was awful. This meant I could not file my UK VAT (sales/purchase tax) quarterly return online until I was in Johannesburg airport en route home where the access was great and I could catch up plus do a lot of email processing.
That was back in the early days of AutoFocus and I recall tagging some tasks 'JNB' = Johannesburg International Airport code.
Reply by Lillian
Mark - are the old/new lists roughly equivalent to the Backlog/Active lists from the original AF4 instructions?
Reply by Alan Baljeu
Lillian: yes but much shorter. Expect much faster dismissal of the closed list because things never :move: into the open list but rather the other two lists.
Roger: The newest system will work exceptionally well in OneNote, yes. Based on it's similarities to My System, I expect it to be a major step up from AF4 in effectiveness. I would consider following it but I'm currently experimenting with a SuperFocus-based project system.
If you were doing OneNote also for home, create a second notebook.
Roger: The newest system will work exceptionally well in OneNote, yes. Based on it's similarities to My System, I expect it to be a major step up from AF4 in effectiveness. I would consider following it but I'm currently experimenting with a SuperFocus-based project system.
If you were doing OneNote also for home, create a second notebook.
Reply by Kiwi Erik
Thanks for clarifying your instructions, Mark -- it now makes perfect sense which page the initial list of 10-20 tasks should go onto.
I must admit, though, that I'm a bit nervous about one aspect of this new system: because there's no dismissal of unfinished tasks, I can see myself getting into the situation where I make some progress on a task, but the task then languishes on the unfinished list and I never make any further progress on it.
Since I always seem to have more to do than time available, wouldn't this new system result in working on the "new" page to avoid items being dismissed, and then working a bit on the easy/interesting/rewarding "unfinished" tasks, without ever getting to those more difficult, less interesting, or unrewarding tasks because there's always something else you could work on instead? Since there's always going to be more to do than time available, wouldn't the unfinished task list keep growing (at least for tasks that can't be finished in one go) and eventually this list would get stale?
I'm also not convinced that I'd have such a large proportion of recurring tasks. Looking at my current DWM2 list, I can see my tasks would be grouped like this:
New/Old: 31 tasks.
Unfinished: 7 tasks.
Recurring: 3 tasks.
In other words, the vast majority of the work I'm doing is various one-off projects (home, hobby or work related), some of which I've started, others are still waiting and I haven't made any progress on yet (and some of these will no doubt get dismissed). But I only have 3 (out of a total of 41) tasks which could be considered to be recurring: replying to emails, folding washing, and tidying the kitchen. Everything else on my list is a one-off task or project.
Maybe I'm mis-understanding what you mean by a recurring task -- or maybe my life is just different from your's...
One of the things that really appeals to me with your DWM system (and your simply brilliant DWM2 variation where everything is on a single list) is that every item is sitting on the "conveyor belt of doom" -- there's a limited amount of time in which to do an item, and if I don't make any progress on it in that time, the item gets dismissed. End of story -- there's no finessing the system or possibility of cheating. And things would definitely never languish on the list because there's no dismissal of unfinished tasks...
Or maybe I'm just mis-understanding how your new system works! I really should try it, though I must confess that I'm a bit leery of doing so because DWM2 is working so incredibly well for me. If it ain't broke...
I must admit, though, that I'm a bit nervous about one aspect of this new system: because there's no dismissal of unfinished tasks, I can see myself getting into the situation where I make some progress on a task, but the task then languishes on the unfinished list and I never make any further progress on it.
Since I always seem to have more to do than time available, wouldn't this new system result in working on the "new" page to avoid items being dismissed, and then working a bit on the easy/interesting/rewarding "unfinished" tasks, without ever getting to those more difficult, less interesting, or unrewarding tasks because there's always something else you could work on instead? Since there's always going to be more to do than time available, wouldn't the unfinished task list keep growing (at least for tasks that can't be finished in one go) and eventually this list would get stale?
I'm also not convinced that I'd have such a large proportion of recurring tasks. Looking at my current DWM2 list, I can see my tasks would be grouped like this:
New/Old: 31 tasks.
Unfinished: 7 tasks.
Recurring: 3 tasks.
In other words, the vast majority of the work I'm doing is various one-off projects (home, hobby or work related), some of which I've started, others are still waiting and I haven't made any progress on yet (and some of these will no doubt get dismissed). But I only have 3 (out of a total of 41) tasks which could be considered to be recurring: replying to emails, folding washing, and tidying the kitchen. Everything else on my list is a one-off task or project.
Maybe I'm mis-understanding what you mean by a recurring task -- or maybe my life is just different from your's...
One of the things that really appeals to me with your DWM system (and your simply brilliant DWM2 variation where everything is on a single list) is that every item is sitting on the "conveyor belt of doom" -- there's a limited amount of time in which to do an item, and if I don't make any progress on it in that time, the item gets dismissed. End of story -- there's no finessing the system or possibility of cheating. And things would definitely never languish on the list because there's no dismissal of unfinished tasks...
Or maybe I'm just mis-understanding how your new system works! I really should try it, though I must confess that I'm a bit leery of doing so because DWM2 is working so incredibly well for me. If it ain't broke...
Reply by nuntym
+Ad Jesum Per Mariam+
Mark,
Ahhhh, now I can see why you said you got your new AF4 tweak from using DWM2 as I use it. You separated the Recurring, Unfinished, New and Old tasks and found a way to work on each separately yet seamlessly instead of working on them mixed up in DWM2...Brilliant! And frankly, I'm pretty flattered. Thanks.
However, like Kiwi Erik, DWM2 is still working very well, especially now that I am using SPP with it, so I probably will have to pass for now. Sorry.
-----
Kiwi Erik,
I would suggest using DWM2 first at least until you have reached the 30th day mark, since it is working very well for you.
-----
Roger J,
I'm very glad the maintenance checklists are still working very well for you. And hey, I'm using them again now, too! Yay us!
-----
God bless!
Mark,
Ahhhh, now I can see why you said you got your new AF4 tweak from using DWM2 as I use it. You separated the Recurring, Unfinished, New and Old tasks and found a way to work on each separately yet seamlessly instead of working on them mixed up in DWM2...Brilliant! And frankly, I'm pretty flattered. Thanks.
However, like Kiwi Erik, DWM2 is still working very well, especially now that I am using SPP with it, so I probably will have to pass for now. Sorry.
-----
Kiwi Erik,
I would suggest using DWM2 first at least until you have reached the 30th day mark, since it is working very well for you.
-----
Roger J,
I'm very glad the maintenance checklists are still working very well for you. And hey, I'm using them again now, too! Yay us!
-----
God bless!
Reply by nuntym
+Ad Jesum Per Mariam+
Roger J,
<>
I think the "Completion Obsession" bug has claimed another victim ^___^
God bless!
Roger J,
<>
I think the "Completion Obsession" bug has claimed another victim ^___^
God bless!
Reply by FocusGuy.
Just to say I could not resist to test the new AF4 revised this morning with 17 tasks.
Some are very precise : example Call Car insurance to negociate price, some others are more general example work on project CERGY (it's a town where i have a building to sale) and i take my tasks on thje project itself which is on my computer.
The result is very interesting. I made all urgent and important things this morning ! . ie 6 MIT
Now, I know exactly what is OLD, NEW, UNFINISHED ie 5 tasks lefts and 2 crossed and I know my RECURRING one task for the moment (I can work on little by little on my current initiative).
I was a bit uncomfortable with my URGENT TASKS but i realized that for a reason I don't know that urgent and important tasks stand at me first and i did it immediately.
For the moment I made it with 3 stapled pages because I wanted to keep my pages by topic i mean all the pages OLD& NEW, RECURRING, UNFINISHED
So I can easily take some time for My 2 others process COLLECT my stuff on my work flow and ANALYSE (ie work on each project and decide what i have to do and when or what I decide not to do too) and I just have to report the next's actions on AF4 R.
I also report on AF4R my incoming tasks as they come on my work flow and tasks coming from my reviews (Ie ical, Mails and so on...).
For treating things and acting I use the QUICK SCAN method and the Stand OUT action explained in AF mark method and so well resumed by Ubi (I love it) even if it is for SF http://www.markforster.net/forum/post/1321345
The system is like for AF4 very addictive and it make me do things and it's great.
Some are very precise : example Call Car insurance to negociate price, some others are more general example work on project CERGY (it's a town where i have a building to sale) and i take my tasks on thje project itself which is on my computer.
The result is very interesting. I made all urgent and important things this morning ! . ie 6 MIT
Now, I know exactly what is OLD, NEW, UNFINISHED ie 5 tasks lefts and 2 crossed and I know my RECURRING one task for the moment (I can work on little by little on my current initiative).
I was a bit uncomfortable with my URGENT TASKS but i realized that for a reason I don't know that urgent and important tasks stand at me first and i did it immediately.
For the moment I made it with 3 stapled pages because I wanted to keep my pages by topic i mean all the pages OLD& NEW, RECURRING, UNFINISHED
So I can easily take some time for My 2 others process COLLECT my stuff on my work flow and ANALYSE (ie work on each project and decide what i have to do and when or what I decide not to do too) and I just have to report the next's actions on AF4 R.
I also report on AF4R my incoming tasks as they come on my work flow and tasks coming from my reviews (Ie ical, Mails and so on...).
For treating things and acting I use the QUICK SCAN method and the Stand OUT action explained in AF mark method and so well resumed by Ubi (I love it) even if it is for SF http://www.markforster.net/forum/post/1321345
The system is like for AF4 very addictive and it make me do things and it's great.
Reply by FocusGuy.
Mark
I have a little doubt about the instruction. I red the forum but i dont really understand what really goes to the UNFINISHED pages.
Let's say I have to call client X - I can't reach him. So I let him a message and cross my OLD PAGE item "Call Client X for subject Y and I report on my UNFINISHED page "Wait for call back Client X". Is that the right way to do it or does it go on NEW page.
Let's say now I wrote on my OLD tasks "Treat taxes with my acountant - Call him first ".
he says ok but I must send him some files. Then Do I put on the NEW page "Send by email acount files" for it is a NEW task or does it go on the UNFINISHED page for it is linked to the unfinished task ?
What really goes on the UNFINISHED page ?.
The instruction said "if you haven't finished a task re enter it on the unfinished page" is not very clear for me. You may put there some thing your are currently working or waiting for and so on...
Would you precise this point ?
Many thanks ideed
I have a little doubt about the instruction. I red the forum but i dont really understand what really goes to the UNFINISHED pages.
Let's say I have to call client X - I can't reach him. So I let him a message and cross my OLD PAGE item "Call Client X for subject Y and I report on my UNFINISHED page "Wait for call back Client X". Is that the right way to do it or does it go on NEW page.
Let's say now I wrote on my OLD tasks "Treat taxes with my acountant - Call him first ".
he says ok but I must send him some files. Then Do I put on the NEW page "Send by email acount files" for it is a NEW task or does it go on the UNFINISHED page for it is linked to the unfinished task ?
What really goes on the UNFINISHED page ?.
The instruction said "if you haven't finished a task re enter it on the unfinished page" is not very clear for me. You may put there some thing your are currently working or waiting for and so on...
Would you precise this point ?
Many thanks ideed
Reply by Roger J
Apologies to all, I think I'm having a 'senior moment'!
1. Assume one has a Recurring Task 'Incremental back-up' which for the first time is entered as a New Task.
2. You do the incremental back-up and cross out the task in the New Tasks page/section.
3. As you know it's a recurring task, you enter 'Incremental back-up' into the Recurring Tasks page/section.
4. Later you get around to doing another incremental back-up. If you do cross it out in the Recurring Tasks page/section, does it get entered again at the bottom of the Recurring Tasks page/section?
If so, why bother? Why not give it a pencil tick to feel good for having done it, then later on erase the pencil tick so that status of the task - in its original location in the Recurring Tasks page/section - reverts back to 'not yet done'?
Or is the answer that because one usually has so many recurring tasks (typical maintenance task types) that one still re-enters at the end of the list to demonstrate achievement and progress?
From the various recurring tasks mentioned in this thread, eg laundry, cleaning, garbage bin, incremental back-ups etc, maybe a more efficient way would be, in the case of weekly or monthly tasks, to enter the tasks into a master list, set a reminder when they should be done (even if the tasks are done on different days during the week), then just tick them off in pencil until the last one is done. Then the tick/tag could be erased and ready for the first one in the new week cycle.
This would leave other recurring tasks to cover the irregular ones.
I think on another blog or page of this site, someone else (Christian?) has raised this issue,
It's been a long day, sorry for any confusion.
1. Assume one has a Recurring Task 'Incremental back-up' which for the first time is entered as a New Task.
2. You do the incremental back-up and cross out the task in the New Tasks page/section.
3. As you know it's a recurring task, you enter 'Incremental back-up' into the Recurring Tasks page/section.
4. Later you get around to doing another incremental back-up. If you do cross it out in the Recurring Tasks page/section, does it get entered again at the bottom of the Recurring Tasks page/section?
If so, why bother? Why not give it a pencil tick to feel good for having done it, then later on erase the pencil tick so that status of the task - in its original location in the Recurring Tasks page/section - reverts back to 'not yet done'?
Or is the answer that because one usually has so many recurring tasks (typical maintenance task types) that one still re-enters at the end of the list to demonstrate achievement and progress?
From the various recurring tasks mentioned in this thread, eg laundry, cleaning, garbage bin, incremental back-ups etc, maybe a more efficient way would be, in the case of weekly or monthly tasks, to enter the tasks into a master list, set a reminder when they should be done (even if the tasks are done on different days during the week), then just tick them off in pencil until the last one is done. Then the tick/tag could be erased and ready for the first one in the new week cycle.
This would leave other recurring tasks to cover the irregular ones.
I think on another blog or page of this site, someone else (Christian?) has raised this issue,
It's been a long day, sorry for any confusion.
Reply by Alan Baljeu
Kiwi,
<>
Not so.
a) Stuff only gets dismissed from the Old list, not the New list.
b) You only need to work one item from the Old list.
c) There's no penalty in the system for working lots and lots on any of the four lists.
d) You naturally want to get the Unfinished list empty, so you will naturally limit time spent on the Old/New, and maximize time spent on Unfinished, so as to clear things out.
The only question is whether you need a clock to push you along regularly.
<
Not so.
a) Stuff only gets dismissed from the Old list, not the New list.
b) You only need to work one item from the Old list.
c) There's no penalty in the system for working lots and lots on any of the four lists.
d) You naturally want to get the Unfinished list empty, so you will naturally limit time spent on the Old/New, and maximize time spent on Unfinished, so as to clear things out.
The only question is whether you need a clock to push you along regularly.
Reply by Alan Baljeu
Roger,
For a long time now I've put regularly recurring items on a calendar, and pulled them out to my AF list when the time comes ready. I also have lists for daily items that I pull out daily.
Things like grocery shopping (which for me is quite irregular), don't actually need to be managed as a recurring item. I know I need more food when I finish something.
Finally, we have yard work. I should do it regularly, but it is of low importance to me, so I do it only when I'm not overly busy or it has been neglected too long. That's perfect for a Recurring list, and it's very nice to have a record of having done it recently. I know because it's close to the bottom of that list.
For a long time now I've put regularly recurring items on a calendar, and pulled them out to my AF list when the time comes ready. I also have lists for daily items that I pull out daily.
Things like grocery shopping (which for me is quite irregular), don't actually need to be managed as a recurring item. I know I need more food when I finish something.
Finally, we have yard work. I should do it regularly, but it is of low importance to me, so I do it only when I'm not overly busy or it has been neglected too long. That's perfect for a Recurring list, and it's very nice to have a record of having done it recently. I know because it's close to the bottom of that list.
Reply by Roger J
Alan:
This seems to me to tie in with Mark's earlier response that daily/time-bound stuff does not belong in AF.
I'm happy with that approach as I already have these daily/weekly/monthly checklists sitting in Listpro.
But I very rarely enter them into AF/DWM. Maybe I should, but it seems like an awful lot of re-writing and yes, I agree that the act of writing does help 'cement' awareness, but it is surely better just to have a 'Check Weekly Tasks' task somewhere, but weekly does not necessarily mean all on one day.
Maybe a repocketmod - http://repocketmod.com/ - piece of paper is the answer, one per week, inserted into an AF paper notebook or wallet, or just have Outlook nag which i know it can do, but which I often resist, for whatever subliminal reasons.
Hmmmm.
This seems to me to tie in with Mark's earlier response that daily/time-bound stuff does not belong in AF.
I'm happy with that approach as I already have these daily/weekly/monthly checklists sitting in Listpro.
But I very rarely enter them into AF/DWM. Maybe I should, but it seems like an awful lot of re-writing and yes, I agree that the act of writing does help 'cement' awareness, but it is surely better just to have a 'Check Weekly Tasks' task somewhere, but weekly does not necessarily mean all on one day.
Maybe a repocketmod - http://repocketmod.com/ - piece of paper is the answer, one per week, inserted into an AF paper notebook or wallet, or just have Outlook nag which i know it can do, but which I often resist, for whatever subliminal reasons.
Hmmmm.
Reply by Kiwi Erik
Hi Alan:
<a) Stuff only gets dismissed from the Old list, not the New list.
b) You only need to work one item from the Old list.
c) There's no penalty in the system for working lots and lots on any of the four lists.
d) You naturally want to get the Unfinished list empty, so you will naturally limit time spent on the Old/New, and maximize time spent on Unfinished, so as to clear things out.
The only question is whether you need a clock to push you along regularly.>>
Thanks for this. Unfortunately, I don't think you've quite understood what I was getting at. In response to your point (a), yes, stuff does get dismissed from the old list, but with this system the old and new items are both on a single page (or series of pages), and dismissal happens from that page. That's what I meant by the "new" page -- sorry, I should have said "new/old" page.
More generally, though, I do see never getting to some tasks as a serious problem. The thing is that items are constantly moving around on the lists -- new items get added, existing items get worked on, sometimes finished and sometimes re-entered. With this constant flow of work, I can see it being very easy indeed for items on the "unfinished" list to just sit there and never get done.
For example, I have a number of unfinished projects which I'm working on "little and often":
* Tidying my office.
* Working through my paperwork backlog.
* Working through my email backlog.
* Typing up a bunch of notes from a workshop I attended a month ago.
* Reading a book.
* Removing nails from a stack of timber currently sitting in my garage.
* Building a new garden wall.
With Mark's new system, these would all end up on the "unfinished" page. But at any one moment, that page would almost certainly include a number of high-priority tasks which need to get worked on as well -- for example, preparing for a meeting, or working towards a major work deadline. When working on the "unfinished" page, these higher priority / more urgent tasks would generally end up trumping the lower priority and less urgent tasks such as those I listed above. And since there's always going to be at least one task that's yelling out to be done, I can see many of the above tasks simply sitting there and never getting attended to.
That's what DWM does -- it applies an (admitted artificial) urgency to tasks that wouldn't otherwise stand out. This forces you to face up and either work on a task to move it forward, or else to dismiss the task and admit that it isn't going to get done. With DWM, I know that I'll be able to keep all these "little and often" projects moving forward, even though there's no inherent urgency in any of them. With Mark's new version of AF4, I can't see that happening.
Or maybe I've mis-understood the way in which Mark's new system is supposed to work...
<
b) You only need to work one item from the Old list.
c) There's no penalty in the system for working lots and lots on any of the four lists.
d) You naturally want to get the Unfinished list empty, so you will naturally limit time spent on the Old/New, and maximize time spent on Unfinished, so as to clear things out.
The only question is whether you need a clock to push you along regularly.>>
Thanks for this. Unfortunately, I don't think you've quite understood what I was getting at. In response to your point (a), yes, stuff does get dismissed from the old list, but with this system the old and new items are both on a single page (or series of pages), and dismissal happens from that page. That's what I meant by the "new" page -- sorry, I should have said "new/old" page.
More generally, though, I do see never getting to some tasks as a serious problem. The thing is that items are constantly moving around on the lists -- new items get added, existing items get worked on, sometimes finished and sometimes re-entered. With this constant flow of work, I can see it being very easy indeed for items on the "unfinished" list to just sit there and never get done.
For example, I have a number of unfinished projects which I'm working on "little and often":
* Tidying my office.
* Working through my paperwork backlog.
* Working through my email backlog.
* Typing up a bunch of notes from a workshop I attended a month ago.
* Reading a book.
* Removing nails from a stack of timber currently sitting in my garage.
* Building a new garden wall.
With Mark's new system, these would all end up on the "unfinished" page. But at any one moment, that page would almost certainly include a number of high-priority tasks which need to get worked on as well -- for example, preparing for a meeting, or working towards a major work deadline. When working on the "unfinished" page, these higher priority / more urgent tasks would generally end up trumping the lower priority and less urgent tasks such as those I listed above. And since there's always going to be at least one task that's yelling out to be done, I can see many of the above tasks simply sitting there and never getting attended to.
That's what DWM does -- it applies an (admitted artificial) urgency to tasks that wouldn't otherwise stand out. This forces you to face up and either work on a task to move it forward, or else to dismiss the task and admit that it isn't going to get done. With DWM, I know that I'll be able to keep all these "little and often" projects moving forward, even though there's no inherent urgency in any of them. With Mark's new version of AF4, I can't see that happening.
Or maybe I've mis-understood the way in which Mark's new system is supposed to work...
Reply by Alan Baljeu
I agree then Erik. I would apply a dismissal rule and closed lists to the Unfinished column. Mark didn't think it would be needed though.
Reply by Vegheadjones
Hi Kiwi Erik,
Here's how I have been doing it.
If it is a project with many different steps, * Building a new garden wall, for example, I have been puttin gthat in the unfinished list. But if it is an ongoing project where every step is the same, Tidying my office. * Working through my paperwork backlog.* Working through my email backlog, e.g..s I treat those as recurring tasks. Personally on those tasks (and I have variants for each on my own list) they are recurring chores and not projects that evolve and get completed. (Though I know we will be done with our back logs one day!)
This has the advantage of keeping Unfinished shorter, but recurring of course is now longer. I think that is OK, as it is more important i finish a pressing now project than complete a backlog review, so the implicit AF "prioiritziation" works for me..
Here's how I have been doing it.
If it is a project with many different steps, * Building a new garden wall, for example, I have been puttin gthat in the unfinished list. But if it is an ongoing project where every step is the same, Tidying my office. * Working through my paperwork backlog.* Working through my email backlog, e.g..s I treat those as recurring tasks. Personally on those tasks (and I have variants for each on my own list) they are recurring chores and not projects that evolve and get completed. (Though I know we will be done with our back logs one day!)
This has the advantage of keeping Unfinished shorter, but recurring of course is now longer. I think that is OK, as it is more important i finish a pressing now project than complete a backlog review, so the implicit AF "prioiritziation" works for me..
Reply by Tijl Kindt
Would there be a disadvantage in using the closed/open list paradigm in Unfinished and (possibly) Recurring as well?
I agree with some of the commenters above that tasks may tend to 'sit' in the Unfinished category while other more pressing or less procrastination-inducing tasks get added and completed.
But furthermore, knowing myself, there are definitely some recurring tasks that may benefit from the closed/open list system as well. For example, you'd be amazed how long I can put off cleaning my dishes. I hate doing dishes. Plain and simple. Granted, there will not really be a punishment for not doing a task in the closed section of the Recurring list, since those tasks really do recur, whether I dismiss them or not, but it'll add a sense of guilt if I cheat my way out of it and don't do anything in the closed list of my Recurring tasks.
I agree with some of the commenters above that tasks may tend to 'sit' in the Unfinished category while other more pressing or less procrastination-inducing tasks get added and completed.
But furthermore, knowing myself, there are definitely some recurring tasks that may benefit from the closed/open list system as well. For example, you'd be amazed how long I can put off cleaning my dishes. I hate doing dishes. Plain and simple. Granted, there will not really be a punishment for not doing a task in the closed section of the Recurring list, since those tasks really do recur, whether I dismiss them or not, but it'll add a sense of guilt if I cheat my way out of it and don't do anything in the closed list of my Recurring tasks.
Reply by Alan Baljeu
I can't see any problem doing so for the Unfinished list. But the Recurring list had frequently and infrequently recurring tasks, and separating that out might be trouble.
For dishes, I suggest washing just one dish. If In doing one you feel like doing two, go ahead. Later wash one or two more. Eventually you'll catch up.
Backup plan: sell half your dishes.
For dishes, I suggest washing just one dish. If In doing one you feel like doing two, go ahead. Later wash one or two more. Eventually you'll catch up.
Backup plan: sell half your dishes.
Reply by Mark Forster
Kiwi:
<< If it ain't broke... >>
Exactly. There's no compulsion on anyone to try out any of my (or anyone else's) new systems.
<< If it ain't broke... >>
Exactly. There's no compulsion on anyone to try out any of my (or anyone else's) new systems.
Reply by Mark Forster
Jupiter:
<< he instruction said "if you haven't finished a task re enter it on the unfinished page" is not very clear for me. You may put there some thing your are currently working or waiting for and so on...
Would you precise this point ? >>
Whether a task is finished or not depends on how you phrased it. If you wrote "Call Mr X", then the task is finished when you have called him and left a message. If you wrote "Speak with Mr X", then you haven't finished the task until you've spoken with him. If you wrote "Agree Project with Mr X", then you haven't finished the task until you've come to an agreement with him (or given up trying to).
<< he instruction said "if you haven't finished a task re enter it on the unfinished page" is not very clear for me. You may put there some thing your are currently working or waiting for and so on...
Would you precise this point ? >>
Whether a task is finished or not depends on how you phrased it. If you wrote "Call Mr X", then the task is finished when you have called him and left a message. If you wrote "Speak with Mr X", then you haven't finished the task until you've spoken with him. If you wrote "Agree Project with Mr X", then you haven't finished the task until you've come to an agreement with him (or given up trying to).
Reply by Mark Forster
Roger:
<< If so, why bother? Why not give it a pencil tick to feel good for having done it, then later on erase the pencil tick so that status of the task - in its original location in the Recurring Tasks page/section - reverts back to 'not yet done'? >>
You might wish to consider some of the following:
1) Crossing a task out is much more satisfying than ticking it.
2) Erasing a pencil tick is messy, especially when you've done it more than once.
3) Erasing a pencil tick needs another two tools (pencil and eraser) in addition to pen and paper.
4) Re-writing a task commits one to doing it in a way which erasing a pencil mark doesn't.
5) You can't see how you have progressed.
6) You may find your list spreads over more pages than when tasks are crossed out.
7) You can't easily see which tasks you have been neglecting.
<< If so, why bother? Why not give it a pencil tick to feel good for having done it, then later on erase the pencil tick so that status of the task - in its original location in the Recurring Tasks page/section - reverts back to 'not yet done'? >>
You might wish to consider some of the following:
1) Crossing a task out is much more satisfying than ticking it.
2) Erasing a pencil tick is messy, especially when you've done it more than once.
3) Erasing a pencil tick needs another two tools (pencil and eraser) in addition to pen and paper.
4) Re-writing a task commits one to doing it in a way which erasing a pencil mark doesn't.
5) You can't see how you have progressed.
6) You may find your list spreads over more pages than when tasks are crossed out.
7) You can't easily see which tasks you have been neglecting.
Reply by Mark Forster
Vegheadjones
<< Tidying my office. * Working through my paperwork backlog.* Working through my email backlog, >>
Those are exactly the sort of tasks I envisaged going in the unfinished column!
<< Tidying my office. * Working through my paperwork backlog.* Working through my email backlog, >>
Those are exactly the sort of tasks I envisaged going in the unfinished column!
Reply by Roger J
Tijl:
Or, buy/marry a dishwasher (ok, girls, only joking).
Mark:
Yes, good points, my post was more of a senior moment.
Anyone:
Would not it be viable to enter a DWM dismissal date when entering an unfinished task?
By 'unfinished task' I mean the specific task and not the whole project. To use Mark's oft-quoted example, an unfinished task would be 'War & Peace: finish chapter 3' whereas its project scope would be 'Read War & Peace'.
I'm still using DWM2 variant and having passed the 28 day mark in my current list, I'm finding the focus on those upcoming dismissal dates a boon.
One can also enter a 7 day dismissal date for re-entered, yet still unfinished tasks.
Or, buy/marry a dishwasher (ok, girls, only joking).
Mark:
Yes, good points, my post was more of a senior moment.
Anyone:
Would not it be viable to enter a DWM dismissal date when entering an unfinished task?
By 'unfinished task' I mean the specific task and not the whole project. To use Mark's oft-quoted example, an unfinished task would be 'War & Peace: finish chapter 3' whereas its project scope would be 'Read War & Peace'.
I'm still using DWM2 variant and having passed the 28 day mark in my current list, I'm finding the focus on those upcoming dismissal dates a boon.
One can also enter a 7 day dismissal date for re-entered, yet still unfinished tasks.
Reply by Alan Baljeu
Sure, Why not?
Reply by Kiwi Erik
Mark:
<>
I understand that, of course...though I am keen to try out your new systems when you've had so much success with them. I'm just surprised that you (and others) haven't found that tasks tend to get neglected once they're on the unfinished list if they can just sit on that list forever. Also, I'm surprised as the sheer number of recurring tasks you reported, when I have almost none.
Vegheadjones:
<>
Personally, I'd find putting backlog-processing onto a "recurring" list would be incredibly demoralising, as that suggests that the backlog would never be finished. But I do see your point...having fewer items in the unfinished list would make it easier to get through them all.
Alan:
<< I agree then Erik. I would apply a dismissal rule and closed lists to the Unfinished column. Mark didn't think it would be needed though.>>
Yes, that would work...applying AF4 dismissal rules to the unfinished page. Interesting idea -- thanks!
<
I understand that, of course...though I am keen to try out your new systems when you've had so much success with them. I'm just surprised that you (and others) haven't found that tasks tend to get neglected once they're on the unfinished list if they can just sit on that list forever. Also, I'm surprised as the sheer number of recurring tasks you reported, when I have almost none.
Vegheadjones:
<
Personally, I'd find putting backlog-processing onto a "recurring" list would be incredibly demoralising, as that suggests that the backlog would never be finished. But I do see your point...having fewer items in the unfinished list would make it easier to get through them all.
Alan:
<< I agree then Erik. I would apply a dismissal rule and closed lists to the Unfinished column. Mark didn't think it would be needed though.>>
Yes, that would work...applying AF4 dismissal rules to the unfinished page. Interesting idea -- thanks!
Reply by Alan Baljeu
<>
Make the backlog a closed list. Now your recurrent task will finish because the backlog is shrinking. Morale restored :-)
Make the backlog a closed list. Now your recurrent task will finish because the backlog is shrinking. Morale restored :-)
Reply by Vegheadjones
Mark:
<< Tidying my office. * Working through my paperwork backlog.* Working through my email backlog, >>
Ha, shows you what I know!
I have been putting large projects with descrete steps on the unfinished list, crossing off a completed step and adding a new one until the project is done. I always treated In box processing and office cleaning as daily (or more often) recurring tasks and have formalized the distinction in revised AF4. I do like having the unfinished work be the important projects in my life and not the routine things...
<< Tidying my office. * Working through my paperwork backlog.* Working through my email backlog, >>
Ha, shows you what I know!
I have been putting large projects with descrete steps on the unfinished list, crossing off a completed step and adding a new one until the project is done. I always treated In box processing and office cleaning as daily (or more often) recurring tasks and have formalized the distinction in revised AF4. I do like having the unfinished work be the important projects in my life and not the routine things...
Reply by FocusGuy.
"I agree then Erik. I would apply a dismissal rule and closed lists to the Unfinished column. Mark didn't think it would be needed though. Alan Baljeu
I totally agree with Alan and Erik.
I found natural to cross a line after my unfinished tasks and treat them as an old list and apply the dissmiss rules.
It works very well and I noticed that this list becomes such like a "golden list" ie a list of all my very important tasks i am dealing with.
This is great.
I totally agree with Alan and Erik.
I found natural to cross a line after my unfinished tasks and treat them as an old list and apply the dissmiss rules.
It works very well and I noticed that this list becomes such like a "golden list" ie a list of all my very important tasks i am dealing with.
This is great.
Reply by Rainer
Well, where does this lead us to? Three different lists? An AF4 list for old/new tasks, an AF4 list for unfinished/partially-finished tasks, and an AF1 list for recurring tasks?
Reply by FocusGuy.
Absolutely Rainer !
or my part I reported all my tasks from my digital system because I wanted to stick to the method and see how my intuition and rational feeling would accept ant treat it.
I never felt so quiet since the beginning of AF and AF4
There is a real feeling of control. And thanks to Mark who explained to me how i could treat the unfinished list (see my thread before) - Thanks Mark ! - I notice than separating the list in OLD, NEW, RECURRING, UNFINISHED and TICKLER is efficient indeed in my way of working.
I dont need context anymore. When i see an item my brain just tell me "eh boy what's the best way to treat it ? a Call ?, an email ?, a letter ?, erase i ?, just guess and do it, can i do it now ?
I also noticed that i could re formulate the item on my unfinished list ie
Ie Call all the clients about project X which in unfinished and take some some blocked time to do it... And now i do it.
But i still put the bigs rocks of my projects and use my calendar as i must do.
or my part I reported all my tasks from my digital system because I wanted to stick to the method and see how my intuition and rational feeling would accept ant treat it.
I never felt so quiet since the beginning of AF and AF4
There is a real feeling of control. And thanks to Mark who explained to me how i could treat the unfinished list (see my thread before) - Thanks Mark ! - I notice than separating the list in OLD, NEW, RECURRING, UNFINISHED and TICKLER is efficient indeed in my way of working.
I dont need context anymore. When i see an item my brain just tell me "eh boy what's the best way to treat it ? a Call ?, an email ?, a letter ?, erase i ?, just guess and do it, can i do it now ?
I also noticed that i could re formulate the item on my unfinished list ie
Ie Call all the clients about project X which in unfinished and take some some blocked time to do it... And now i do it.
But i still put the bigs rocks of my projects and use my calendar as i must do.
Reply by Mark T
Does this mean I should switch from SAF to Revised AF4?
What is the consensus here? Is Revised AF4 better or just different?
What is the consensus here? Is Revised AF4 better or just different?
Reply by Christian G.
Sorry, but I'm still not sure how to treat real multi-step projects with a separate project plan. I actually see them as recurring tasks since I need to revisit them over and over again until the project is finished (I don't like to see them as unfinished). Well, I'm actually experimenting with a separate project page (thus having four types of pages: OLD/NEW, PROJECTS, RECURRING, UNFINISHED - in that order). The PROJECTS page is treated like the RECURRING page. What do you think?
Reply by Alan Baljeu
Mark T,
Revised AF4 is very like AF4. People are still figuring out AF4R. There's a lot of confusion about where things fit. I haven't seen any success reports yet. I think it's too soon to say for sure.
SAF is very like AF1. I know some people have liked it much. Did you? I haven't heard much of SAF success or failure.
The big question is, how easy is it to use?
Revised AF4 is very like AF4. People are still figuring out AF4R. There's a lot of confusion about where things fit. I haven't seen any success reports yet. I think it's too soon to say for sure.
SAF is very like AF1. I know some people have liked it much. Did you? I haven't heard much of SAF success or failure.
The big question is, how easy is it to use?
Reply by Seraphim
MarkT:
<<>>
I like them both and am trying out combining them. So far, I really like it. See <http://www.markforster.net/forum/post/1330080>.
<<
I like them both and am trying out combining them. So far, I really like it. See <http://www.markforster.net/forum/post/1330080>.
Reply by Seraphim
Christian G:
<<>>
I am handling it like this.
If I work on a project, and need to stop for the moment, but feel I need to get back to it right away, I re-enter it as Unfinished.
But if I made good progress, or reached a milestone, or otherwise feel I am "done for now", then I re-enter it as Old/New.
This is very similar to what Mark was recommending for SAF:
"Done for now" = put it at the end of the list
"Need to keep working on it" = put it in the 2nd column
<<
I am handling it like this.
If I work on a project, and need to stop for the moment, but feel I need to get back to it right away, I re-enter it as Unfinished.
But if I made good progress, or reached a milestone, or otherwise feel I am "done for now", then I re-enter it as Old/New.
This is very similar to what Mark was recommending for SAF:
"Done for now" = put it at the end of the list
"Need to keep working on it" = put it in the 2nd column
Reply by Scott Hutchins
Let's say I'm working on a project...It starts in the "NEW" list. Once I do something on it, should the general rule be to put my re-entry on the "UNFINISHED" list (because the project is started but not complete) or on the "NEW" list (if the next step of the project is a whole new and different task than what I've been engaged in so far)?
Also, do people tend to put their MUST DO TODAY and won't do until a LATER DATE tasks in calendars/ticklers/etc? I want to keep everything in one place, but in practice it seems to cause clutter and confusion. SAF sounds like a good way to separate today's items...
Interesting stuff...thanks Mark!!!
Also, do people tend to put their MUST DO TODAY and won't do until a LATER DATE tasks in calendars/ticklers/etc? I want to keep everything in one place, but in practice it seems to cause clutter and confusion. SAF sounds like a good way to separate today's items...
Interesting stuff...thanks Mark!!!
Reply by Alan Baljeu
Write whatever you want done. It's up to you how big an item you write. If you start that item but don't finish, move it to Unfinished. When you finish that item, enter something new in New.
I put dated items in ticklers, and pull them out when the day arrives.
I put dated items in ticklers, and pull them out when the day arrives.
Reply by FocusGuy.
@Scott - "Let's say I'm working on a project...It starts in the "NEW" list. Once I do something on it, should the general rule be to put my re-entry on the "UNFINISHED" list (because the project is started but not complete) or on the "NEW" list (if the next step of the project is a whole new and different task than what I've been engaged in so far)?"
I hope i understand when you question if i don't please don't hesitate to correct me.
Well, you start a project : let's say "Tidy my office" because you have a lot of stuff everywhere on the floor and so on.
This project has many tasks such as tidy the shelves, tidy the floor, tidy my desc...
As you start this project, you cross it on your new list and the project is reported on the unfinished list and reformulated, like for example "finish to tidy my office"
little by little tasks will come on the new list, if finished will be crossed and if unfinished will go on the unfinished list as "finish to tidy my desk"
If the project is very complicated with steps and so on you can take some time to work onit, plan it, put some dates on your diary (deadlines ? - things you are waiting from others...) and work on a special project sheet (a word sheet for example) where you will put the bigs rocks about it ie DESK, SHELVES, FLOOR...
So, little by little, you will input in your list what you must do.
Hope it's clear. This is how I use AF4R. What is interesting is that many project goes on The new list AND then later when they are engaged, BUT NOT FINISHED, they go on the unfinished list. if they are finished they are crossed. Exactly like my tasks.
I hope i understand when you question if i don't please don't hesitate to correct me.
Well, you start a project : let's say "Tidy my office" because you have a lot of stuff everywhere on the floor and so on.
This project has many tasks such as tidy the shelves, tidy the floor, tidy my desc...
As you start this project, you cross it on your new list and the project is reported on the unfinished list and reformulated, like for example "finish to tidy my office"
little by little tasks will come on the new list, if finished will be crossed and if unfinished will go on the unfinished list as "finish to tidy my desk"
If the project is very complicated with steps and so on you can take some time to work onit, plan it, put some dates on your diary (deadlines ? - things you are waiting from others...) and work on a special project sheet (a word sheet for example) where you will put the bigs rocks about it ie DESK, SHELVES, FLOOR...
So, little by little, you will input in your list what you must do.
Hope it's clear. This is how I use AF4R. What is interesting is that many project goes on The new list AND then later when they are engaged, BUT NOT FINISHED, they go on the unfinished list. if they are finished they are crossed. Exactly like my tasks.
Reply by Scott Hutchins
Alan and Jupiter - thanks for your responses!
I really like separating things I may do/haven't started yet from things that I have started and am committed to. AF4R handles that well with NEW/OLD and UNFINISHED/RECURRING and allows you to see your volume in each context.
There is definitely a similarity here with Kanbans (backlog/do eventually, doing/what you are committed to completing now, and done). My struggle is that I want to quickly and easily identify what I'm most committed to doing NOW. However, that could be on any of the three AF4R lists.
The holy grail of all this AF/DWM/DIT stuff may be finding a way to coordinate the backlog/now/done into a paper list (or lists) that doesn't require much rewriting but really highlights the NOW part. You are constantly pulling from the backlog list, but focusing on a limited NOW. Mark's 3 task trial aligns with that.
I really like separating things I may do/haven't started yet from things that I have started and am committed to. AF4R handles that well with NEW/OLD and UNFINISHED/RECURRING and allows you to see your volume in each context.
There is definitely a similarity here with Kanbans (backlog/do eventually, doing/what you are committed to completing now, and done). My struggle is that I want to quickly and easily identify what I'm most committed to doing NOW. However, that could be on any of the three AF4R lists.
The holy grail of all this AF/DWM/DIT stuff may be finding a way to coordinate the backlog/now/done into a paper list (or lists) that doesn't require much rewriting but really highlights the NOW part. You are constantly pulling from the backlog list, but focusing on a limited NOW. Mark's 3 task trial aligns with that.
Reply by Christian G.
Thanks for all your responses regarding the "project question". I actually regard Seraphims answer as a good way to handle it:
"If I work on a project, and need to stop for the moment, but feel I need to get back to it right away, I re-enter it as Unfinished.
But if I made good progress, or reached a milestone, or otherwise feel I am "done for now", then I re-enter it as Old/New."
BTW: I separate projects from long-dated "little-and-often"-tasks. A project has a proper plan with single steps. milestones, dependencies, ... . On the other hand there are other tasks like "Tidy my office" where I don't have a proper plan. These tasks are reentered as UNFINISHED after each time I worked on it...
"If I work on a project, and need to stop for the moment, but feel I need to get back to it right away, I re-enter it as Unfinished.
But if I made good progress, or reached a milestone, or otherwise feel I am "done for now", then I re-enter it as Old/New."
BTW: I separate projects from long-dated "little-and-often"-tasks. A project has a proper plan with single steps. milestones, dependencies, ... . On the other hand there are other tasks like "Tidy my office" where I don't have a proper plan. These tasks are reentered as UNFINISHED after each time I worked on it...
Reply by Alan Baljeu
Scott,
There is a similarity to Kanban for sure. Even the discussion here on task size is helping me manage the team kanban board better.
Now toward your holy Grail: One approach to Af4r is to deliberately start as few things as possible (in line with3t and kanban). Additionally make the items on the Unfinished list to be medium sized. (You might allow one big item to be your main focus.). So every time you visit the new and old lists, restrict yourself to Small items and very few bigger items. The result should be that the Unfinished list has those things you want to focus on. You finish those, enter next steps as new, and go get some more.
Above is how I operated My System, which is like AF4r without a recurring section. I Found it worked quite well.
There is a similarity to Kanban for sure. Even the discussion here on task size is helping me manage the team kanban board better.
Now toward your holy Grail: One approach to Af4r is to deliberately start as few things as possible (in line with3t and kanban). Additionally make the items on the Unfinished list to be medium sized. (You might allow one big item to be your main focus.). So every time you visit the new and old lists, restrict yourself to Small items and very few bigger items. The result should be that the Unfinished list has those things you want to focus on. You finish those, enter next steps as new, and go get some more.
Above is how I operated My System, which is like AF4r without a recurring section. I Found it worked quite well.
Reply by Erik
I conquer...
The more the list systems of Mark evolve, the more they have the properties of the Kanban.
The more the list systems of Mark evolve, the more they have the properties of the Kanban.
Reply by FocusGuy.
What is kanban ?
Does any one has a link tthe summury of it ?
Thanks .
Does any one has a link tthe summury of it ?
Thanks .
Reply by FocusGuy.
Ok i found it on Mark site ;-)
Reply by Mark Forster
If I knew what the Kanban consisted of I might be able to comment!
Reply by Alan Baljeu
Kanban is a Japanese word meaning signal. It's used in manufacturing where workers put out a card to a spot indicating that somebody downstream needs a part built. These cards might be arranged on a board to indicate an assembly line where a card in column x indicates step x needs to be applied to project x.
As a way to reduce overhead, we aim to minimize the amount of cards flowing across the board. And as a mechanism to encouage this, each column has a fixed limit, such as no more than 3 at stage x.
For personal work, typical cards would be projects or tasks, columns could be Backlog, plan, do, finished, and a strict limit on the do column forces a person to finish unfinshed work.
Kanban also lets you define different groups with different limits. Erik's system defines 5 types of work, and it limits the amount of time spent each day on each.
As a way to reduce overhead, we aim to minimize the amount of cards flowing across the board. And as a mechanism to encouage this, each column has a fixed limit, such as no more than 3 at stage x.
For personal work, typical cards would be projects or tasks, columns could be Backlog, plan, do, finished, and a strict limit on the do column forces a person to finish unfinshed work.
Kanban also lets you define different groups with different limits. Erik's system defines 5 types of work, and it limits the amount of time spent each day on each.
Reply by FocusGuy.
Just found a way to focus on the most important things with the unfinished list !!!!
- Just put the most important tasks on the upper part of the sheet
- Just put the less important tasks on the bottom of the page beginning by the end of the page and going up little by little.
- Just put the most important tasks on the upper part of the sheet
- Just put the less important tasks on the bottom of the page beginning by the end of the page and going up little by little.
Reply by Roger J
Jupiter:
And if your latest UNfinished task is the most important and you've already filled up the top half of the page?
By all means split upper and lower pages for contexts, eg Work and Personal (I used to, now keep separate lists), but you seem to want to prioritise each time you enter an Unfinished task, which itself my already be on the list.
I can't see how that would be effective, but if it works for you . . . .
And if your latest UNfinished task is the most important and you've already filled up the top half of the page?
By all means split upper and lower pages for contexts, eg Work and Personal (I used to, now keep separate lists), but you seem to want to prioritise each time you enter an Unfinished task, which itself my already be on the list.
I can't see how that would be effective, but if it works for you . . . .
Reply by FocusGuy.
Hi Roger
Personal task goes on another notebook and I use AF1 for it.
I never mixt professional and personal things even if i work only at home.
The idea of prioritizing some tasks was to group together some of my most important unfinished or must following and unfinished tasks or project.
eg : I have there some of highest project such as
Waiting for the proposal of client X about building Y
Waiting for the date client X will pay my bill
Waiting for the call of the phone company for an appointment next week
Find an agreement with jenifer about my car's insurance
All these are essential for me.
I noticed that most of the tasks which are at the bottom of my page becomes dismiss very fast.
The chose between the two is very simple. When I realize a task is unfinished I just ask to myself How is it essential for me.
When the page is full I just take another page and report if needed what is left or if they are many I just notice on a corner of my last page > Go to the other page....
Personal task goes on another notebook and I use AF1 for it.
I never mixt professional and personal things even if i work only at home.
The idea of prioritizing some tasks was to group together some of my most important unfinished or must following and unfinished tasks or project.
eg : I have there some of highest project such as
Waiting for the proposal of client X about building Y
Waiting for the date client X will pay my bill
Waiting for the call of the phone company for an appointment next week
Find an agreement with jenifer about my car's insurance
All these are essential for me.
I noticed that most of the tasks which are at the bottom of my page becomes dismiss very fast.
The chose between the two is very simple. When I realize a task is unfinished I just ask to myself How is it essential for me.
When the page is full I just take another page and report if needed what is left or if they are many I just notice on a corner of my last page > Go to the other page....
Reply by Erik
@Alan
Great explanation of what a Kanban is.
Also, you explained my system very precisely and clearly in one sentence!
I've been following your comments on Marks' and you never misinterpret them.
You have a grasp of systems that is uncanny!
Great explanation of what a Kanban is.
Also, you explained my system very precisely and clearly in one sentence!
I've been following your comments on Marks' and you never misinterpret them.
You have a grasp of systems that is uncanny!
Reply by Mark Forster
Alan:
<< These cards might be arranged on a board to indicate an assembly line where a card in column x indicates step x needs to be applied to project x.
As a way to reduce overhead, we aim to minimize the amount of cards flowing across the board. And as a mechanism to encouage this, each column has a fixed limit, such as no more than 3 at stage x. >>
You're confusing me with all these x's! Does the column refer to the step, the project or the stage or all three of them?
<< These cards might be arranged on a board to indicate an assembly line where a card in column x indicates step x needs to be applied to project x.
As a way to reduce overhead, we aim to minimize the amount of cards flowing across the board. And as a mechanism to encouage this, each column has a fixed limit, such as no more than 3 at stage x. >>
You're confusing me with all these x's! Does the column refer to the step, the project or the stage or all three of them?
Reply by Mark Forster
And I still don't see how my systems resemble Kanban!
Reply by Erik
A Kanban depicts a flow through which a certain something goes through to get to a finished state. Each step gives it value of some sort. Three things that Kanban are really good at are:
- Visualizing the work in progress (and by a by-product seeing where things are bogging down)
- Limiting the Work in Progress
- It is a pull system compared to a push system where when things get out to the finished state, it creates an opening for a new something to take it's place. (Flow is dictated by what comes out of the system, not what comes into it).
Your new AF4R has to some extent, those three things, albeit I'll admit that it is not yet a pull system :)
- Visualizing the work in progress (and by a by-product seeing where things are bogging down)
- Limiting the Work in Progress
- It is a pull system compared to a push system where when things get out to the finished state, it creates an opening for a new something to take it's place. (Flow is dictated by what comes out of the system, not what comes into it).
Your new AF4R has to some extent, those three things, albeit I'll admit that it is not yet a pull system :)
Reply by Roger J
Erik/Alan: I think a suitable link to a Kanban software demo (I can't recall the one I looked at a few months ago) would help Mark and others.
Reply by Alan Baljeu
Imagine the following Personal Kanban setup
Here are column headings for two tables:
Backlog | Prepare | Work | Done
Maintainance | Work | Done
Backlog is like New/Old without a rule for dismissing. It collects tasks as you think of them.
Now let's say you choose Clean Yard. Move that card to Prepare.
First step is to get the rake, bags, shears, warm clothes.
Once Prepare is done, move it to Work. This spot is like Unfinished. The task will stay there while you ignore it, work on it, or do something else. The work limits (like 3 in your 3 task system) urge you to get the Yard clean so you can work on something else.
In maintenance, we have recurring items. you would pull an item out of M, work on it, and put it to done when finished. Once done, put it back to Maintenance for the next time.
In fact kanban has one way to encourage dismissal though it isn't often used this way: the column limits. If say you restrict your backlog count to 20, then if you think of a 21st item, you need to dismiss something to make room.
Here are column headings for two tables:
Backlog | Prepare | Work | Done
Maintainance | Work | Done
Backlog is like New/Old without a rule for dismissing. It collects tasks as you think of them.
Now let's say you choose Clean Yard. Move that card to Prepare.
First step is to get the rake, bags, shears, warm clothes.
Once Prepare is done, move it to Work. This spot is like Unfinished. The task will stay there while you ignore it, work on it, or do something else. The work limits (like 3 in your 3 task system) urge you to get the Yard clean so you can work on something else.
In maintenance, we have recurring items. you would pull an item out of M, work on it, and put it to done when finished. Once done, put it back to Maintenance for the next time.
In fact kanban has one way to encourage dismissal though it isn't often used this way: the column limits. If say you restrict your backlog count to 20, then if you think of a 21st item, you need to dismiss something to make room.
Reply by Mark Forster
I do vaguely remember looking at the Kanban software demo someone flagged up some months ago and thinking that I couldn't see how it could possibly work for personal tasks (as opposed to progress on major projects).
I guess the 3T system would be Kanbanesque, in that one takes three tasks and isn't allowed to move on until two of them have been completed, but I can't see that dividing tasks into New, Old, Recurring and Unfinished is in the least bit Kanbanic. As Eric says no pull is created.
Perhaps readers could make suggestions about how to create that pull in AF4R?
I guess the 3T system would be Kanbanesque, in that one takes three tasks and isn't allowed to move on until two of them have been completed, but I can't see that dividing tasks into New, Old, Recurring and Unfinished is in the least bit Kanbanic. As Eric says no pull is created.
Perhaps readers could make suggestions about how to create that pull in AF4R?
Reply by Mark Forster
Alan:
How do you decide when you should be working on the Backlog Table and when on the Maintenance Table?
How long are tasks held in Done before they are transferred back to Maintenance?
What does the Prepare column achieve? Isn't preparation just a part of work - what's the reason for differentiating them? If you have a Prepare column, shouldn't you have a Clear Up column as well?
How do you keep track of all this?
How do you decide when you should be working on the Backlog Table and when on the Maintenance Table?
How long are tasks held in Done before they are transferred back to Maintenance?
What does the Prepare column achieve? Isn't preparation just a part of work - what's the reason for differentiating them? If you have a Prepare column, shouldn't you have a Clear Up column as well?
How do you keep track of all this?
Reply by Alan Baljeu
Hoo boy! Questions.
The fundamental rule is this: you may work anything at any time provided there is room. The goal is to minimize work in progress which minimizes time to finish and maximizes throughput.
As to deciding: Kanban is driven by sight more than by rules. In a team setting you would choose on building screws because the assembler down the line needs screws to assemble something. On a board you would see he's needing screws. But if he's plenty busy you make bolts instead for someone else.
So if you have company coming that pulls vacuuming out. If nothing is urgent you choose whatever you feel like.
Multiple columns aim to standardize work and to divide work across people. In this case it is quite useless, just illustrates what a column might be.
You could have a cleanup column if you like though.
Track: a card on a spot means you need to work on it. There is no historical record of where cards were. It is common to date the cards when they were written or last worked on.
The fundamental rule is this: you may work anything at any time provided there is room. The goal is to minimize work in progress which minimizes time to finish and maximizes throughput.
As to deciding: Kanban is driven by sight more than by rules. In a team setting you would choose on building screws because the assembler down the line needs screws to assemble something. On a board you would see he's needing screws. But if he's plenty busy you make bolts instead for someone else.
So if you have company coming that pulls vacuuming out. If nothing is urgent you choose whatever you feel like.
Multiple columns aim to standardize work and to divide work across people. In this case it is quite useless, just illustrates what a column might be.
You could have a cleanup column if you like though.
Track: a card on a spot means you need to work on it. There is no historical record of where cards were. It is common to date the cards when they were written or last worked on.
Reply by Alan Baljeu
This link explains it better. http://www.personalkanban.com/pk/personal-kanban-101/
Reply by Scott Hutchins
Just a thought...
Time management vary based on focus as much as logistics. GTD (context) Franklin Covey (priority of task/role), Total Workday Control (urgency - when to be done), etc. The kanban discussion tends towards TWC.
Anyway...perhaps instead of separate lists for unfinished, recurring, new and old...What we could do is have them for tasks/projects that are:
- MAYBE (ideas that we haven't committed to acting on yet)
- PENDED (things we are going to do, but not yet: Tickler items with future dates & Someday)
- ASAP or backlog (we are committed to doing them and will do so as soon as they feel ready to be acted upon)
- NOW (those limited items we've pulled from the the pages above to do NOW). These are the items Mark pulled in his 3 task experiment...
You could see tasks flow through these categories and have an idea of the volume of each...plus you would always be able to turn your focus on to the critical items you know you want to do first.
Time management vary based on focus as much as logistics. GTD (context) Franklin Covey (priority of task/role), Total Workday Control (urgency - when to be done), etc. The kanban discussion tends towards TWC.
Anyway...perhaps instead of separate lists for unfinished, recurring, new and old...What we could do is have them for tasks/projects that are:
- MAYBE (ideas that we haven't committed to acting on yet)
- PENDED (things we are going to do, but not yet: Tickler items with future dates & Someday)
- ASAP or backlog (we are committed to doing them and will do so as soon as they feel ready to be acted upon)
- NOW (those limited items we've pulled from the the pages above to do NOW). These are the items Mark pulled in his 3 task experiment...
You could see tasks flow through these categories and have an idea of the volume of each...plus you would always be able to turn your focus on to the critical items you know you want to do first.
Reply by Gerry
After having tried a variety of systems, I find that simply dividing into the categories of what I plan to do today and everything else is as good a system as anything. Most of us know what we really should be doing and working on in a given day. When we resist this, it is not really a time management issue. Triple task like plan your day is a way to think about what needs to be accomplished today.
Gerry
Gerry
Reply by Scott Hutchins
Touché Gerry! A running master task list and a daily list are very effective. When the master (backlog) grows really long, it would be helpful to have something built into the system to regulate prioritizing & pruning...and move stuff along without letting things fall through the cracks.
But, Gerry is right. It's easy to make this more complex than it needs to be.
But, Gerry is right. It's easy to make this more complex than it needs to be.
Reply by Erik
There is a slight difference between kanban and personal kanban.
But first I should point out that a kanban is what you want it to be; you try a sequence of steps with work in progress limits and tweak things as you see problems arise always striving to have the most streamlined process.
The kanban is perfect for teams. The personal kanban goes against that since you are an individual. And as Mark points it out, the are not many columns necessary (to do, doing, done). I personally have also the Checklist from which I take things and put them on the backlog to be processed. I soon figured out that adding columns was complicating things instead of simplifying them and life is not an assembly line. But I needed more power to choose what was important to me now. So I color coded different tasks with different activities. You could do it with areas of life if you prefer.
All is very visual so it's not that hard to decide on what you want to work next and you soon figure out where things get bogged down!
But first I should point out that a kanban is what you want it to be; you try a sequence of steps with work in progress limits and tweak things as you see problems arise always striving to have the most streamlined process.
The kanban is perfect for teams. The personal kanban goes against that since you are an individual. And as Mark points it out, the are not many columns necessary (to do, doing, done). I personally have also the Checklist from which I take things and put them on the backlog to be processed. I soon figured out that adding columns was complicating things instead of simplifying them and life is not an assembly line. But I needed more power to choose what was important to me now. So I color coded different tasks with different activities. You could do it with areas of life if you prefer.
All is very visual so it's not that hard to decide on what you want to work next and you soon figure out where things get bogged down!